Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dev dependency update: @semantic-release/commit-analyzer (major) #40

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

dev dependency update: @semantic-release/commit-analyzer (major) #40

wants to merge 1 commit into from
+5 −5

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 18, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer 11.1.0 -> 13.0.0 age adoption passing confidence
@semantic-release/github 9.2.6 -> 11.0.1 age adoption passing confidence
@semantic-release/npm 11.0.3 -> 12.0.1 age adoption passing confidence
@semantic-release/release-notes-generator 12.1.0 -> 14.0.2 age adoption passing confidence
semantic-release 23.0.2 -> 24.2.0 age adoption passing confidence

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.0

Compare Source

Bug Fixes
  • log the raw message again (e2f5d6c)
Features
  • support latest conventional-changelog packages (0254d7a)
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are
    dropping support for previous major versions of those packages due to the breaking changes between
    majors. this only impacts your project if you are installing alongside semantic-release, so updating
    those packages to latest version should be the only change you need for this update. no action
    should be necessary if you are using default semantic-release config

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (f3358dd)
  • node-versions: dropped support for node v18 and v19 (0a23b82)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported
semantic-release/github (@​semantic-release/github)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

chore
  • update peer dependency for semantic-release (95c7cdd)
Code Refactoring
  • modify commit associatedPRs and relatedIssues label property data type. (718134a)
Features
  • integrate warn in fail script (7a9914a)
  • integrate warn in success script (792720d)
BREAKING CHANGES
  • the commit associatedPR and relatedIssues label prop is now an array of objects with more properties
  • the minimum required version of semantic-release to use
    @​semantic-release/github is now v24.1.0

v10.3.5

Compare Source

Bug Fixes
  • replace searchAPI usage with GraphQL in findSRIssue util (#​907) (7fb46a3)

v10.3.4

Compare Source

v10.3.3

Compare Source

Bug Fixes
  • Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes
  • missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes
  • max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features
  • allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

v10.1.7

Compare Source

Bug Fixes

v10.1.6

Compare Source

v10.1.5

Compare Source

Bug Fixes

v10.1.4

Compare Source

Bug Fixes
  • docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

v10.1.2

Compare Source

Bug Fixes

v10.1.1

Compare Source

Bug Fixes
  • invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

v10.0.7

Compare Source

Bug Fixes
  • replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes
  • corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)

v10.0.3

Compare Source

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-versions: dropped support for node v18 and v19 (#​797) (aea314f)
BREAKING CHANGES
  • node-versions: node v18 and v19 are no longer supported
semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (9e193c2)
  • node-versions: dropped support for node v18 and v19 (2df962b)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported
semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.0.2

Compare Source

v14.0.1

Compare Source

Bug Fixes

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config

v13.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (5655b18)
  • node-versions: dropped support for node v18 and v19 (e65959a)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported
semantic-release/semantic-release (semantic-release)

v24.2.0

Compare Source

Features
  • clarify branch existence requirement in error messages (#​3462) (05a2ea9)

v24.1.3

Compare Source

Bug Fixes
  • branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

v24.1.2

Compare Source

Bug Fixes

v24.1.1

Compare Source

v24.1.0

Compare Source

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

v23.1.1

Compare Source

v23.1.0

Compare Source

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title dev dependency update: @semantic-release/github (major) dev dependency update: @semantic-release/commit-analyzer (major) Mar 18, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4a22765 to 0c3c3fc Compare March 24, 2024 07:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0c3c3fc to 60f0fa5 Compare April 6, 2024 20:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from f61a5f3 to fa51bdd Compare May 16, 2024 00:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fa51bdd to 583c08f Compare May 22, 2024 19:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 11bcbab to f3712b8 Compare June 5, 2024 05:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f3712b8 to a6974d5 Compare June 22, 2024 04:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0b6642e to 5760259 Compare July 8, 2024 14:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from d54dbec to 4916c3d Compare July 17, 2024 17:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 84c5bf4 to 8df0eaa Compare July 26, 2024 01:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 339aaa5 to 152d1ee Compare August 15, 2024 20:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 07f5163 to f7a0ac1 Compare August 20, 2024 20:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 54578d7 to 12c8311 Compare September 6, 2024 00:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d821ce7 to 77439c6 Compare September 15, 2024 15:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 692455e to 3fff35e Compare September 27, 2024 18:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c6f811e to e50a69d Compare October 25, 2024 21:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e50a69d to f956000 Compare November 6, 2024 20:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from b3791a8 to 217cdf9 Compare December 2, 2024 03:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 217cdf9 to d8b3123 Compare December 14, 2024 01:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d8b3123 to 9c25978 Compare December 16, 2024 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants